Skip to content

chore: update versions#593

Closed
rajat1saxena wants to merge 1 commit intorajat1saxena/issue590from
changeset-release/rajat1saxena/issue590
Closed

chore: update versions#593
rajat1saxena wants to merge 1 commit intorajat1saxena/issue590from
changeset-release/rajat1saxena/issue590

Conversation

@rajat1saxena
Copy link
Copy Markdown
Member

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to rajat1saxena/issue590, this PR will be updated.

Releases

@courselit/email-editor@0.1.0

Patch Changes

  • 56bc36a: Testing GH Action and changeset

@courselit/web@0.60.1

Patch Changes

  • Updated dependencies [56bc36a]
    • @courselit/email-editor@0.1.0

All notable changes to this project will be documented in this file.
See Conventional Commits for commit guidelines.

@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
courselit-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 17, 2025 5:12am

@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented Jun 17, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
17913226 Triggered npm Token 9c44707 .npmrc View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@rajat1saxena rajat1saxena deleted the changeset-release/rajat1saxena/issue590 branch June 17, 2025 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant